System and method for storing user data

ABSTRACT

A method and system to store user data are provided. A system to store user data may include a video recorder device. The video recorder device may include a video receiver to receive video data. The video recorder device may also include a memory device. The memory device may include at least one protected memory region to store video data received via the video receiver. The memory device may also include at least one unprotected memory region. The video recorder device may be adapted to prevent user copying of video data stored at the protected memory region and to allow user copying of data stored at the unprotected memory region.

FIELD OF THE DISCLOSURE

The present disclosure is generally related to storing user data.

BACKGROUND

Digital video recorders (DVRs) may record video data to a memory medium,such as a hard drive. For example, some DVRs may be used to recordtelevision programming. In another example, some DVRs may be used torecord video information from security cameras. The memory medium of aDVR may be of sufficient capacity to store both video data and otheruser data. However, it may be undesirable to mix other user data withvideo data on the memory medium. Hence, there is a need for an improvedmethod of storing user data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a particular embodiment of a system tostore user data;

FIG. 2 is flow chart of a first particular embodiment of a method ofstoring user data;

FIG. 3 is flow diagram of a second particular embodiment of a method ofstoring user data;

FIG. 4 is a diagram of a first particular embodiment of a user interfacefor storing user data;

FIG. 5 is a diagram of a second particular embodiment of a userinterface for storing user data;

FIG. 6 is a diagram of a third particular embodiment of a user interfacefor storing user data;

FIG. 7 is a diagram of a fourth particular embodiment of a userinterface for storing user data;

FIG. 8 is a diagram of a fifth particular embodiment of a user interfacefor storing user data; and

FIG. 9 is an illustrative embodiment of a general computer system.

DETAILED DESCRIPTION OF THE DRAWINGS

In a particular embodiment, a system to store user data may include avideo recorder device. The video recorder device may include a videoreceiver to receive video data. The video recorder device may alsoinclude a memory device. The memory device may include at least oneprotected memory region to store video data received via the videoreceiver. The memory device may also include at least one unprotectedmemory region. The video recorder device may be adapted to prevent usercopying of video data stored at the protected memory region and to allowuser copying of data stored at the unprotected memory region.

In a particular embodiment, a method of storing user data may includereceiving video data via a video distribution network. The method mayalso include storing the video data at a protected memory region of amemory device. In an illustrative embodiment, the memory device may beadapted to prevent user copying of data stored in the protected memoryregion. The method may also include receiving user data via a userdevice interface. The method may further include storing the user dataat an unprotected memory region of the memory device. The memory devicemay be adapted to allow user copying of data stored in the unprotectedmemory region

In a particular embodiment, a processor readable medium may includeprocessor readable instructions. The processor readable instructions maybe executable by a processor to receive video data via a videodistribution network. The instructions may also be executable to storethe video data at a protected memory region of a memory device. In anillustrative embodiment, the memory device does not allow user copyingof data stored in the protected memory region. The instructions may alsobe executable to receive user data via at least one user deviceinterface. The instructions may further be executable to store the userdata at one or more unprotected memory regions of the memory device. Thememory device may allow user copying of data stored in the one or moreunprotected memory regions.

FIG. 1 depicts a block diagram of a particular embodiment of a system tostore user data, generally designated 100. The system 100 includes avideo recorder device 102 adapted to receive video data from a serviceprovider 104, for example, via a video distribution network 106. Thevideo recorder device 102 may also provide an output data streamincluding video data to a display device 108. The video recorder device102 may receive user data from user device(s) 140, such as music files(e.g., mp3 files), other media files (e.g., video or still image files),security camera files, or any other user data.

In a particular illustrative embodiment, the video recorder device 102may be a set-top box device, such as a digital video recorder, an IPTVset-top box device, a video gaining device or console adapted to receivevideo content, any other device adapted to receive television content,or any combination thereof. In this embodiment, the video recorderdevice 102 may receive data, video, or any combination thereof, from theservice provider 104 and render or display the data, video, or anycombination thereof, at the display device 108.

In a particular embodiment, the video recorder device 102 may include avideo receiver 112. The video receiver 112 may include a digital tuner,such as an Advanced Television Standards Committee (ATSC) tuner, thatreceives and decodes television programming signals or packet streamsfor transmission to the display device 108. The video receiver may beimplemented in hardware, software or any combination thereof. Forexample, the video receiver 112 may include software executable by logic110.

In a particular embodiment, the video recorder device 102 may include amemory device 120. The memory device 120 may include solid-state memory,magnetic memory, magneto-optical memory, optical memory, any otherprocessor readable memory, or any combination thereof. In a particularembodiment, the memory device 120 may include a system memory region122. The system memory region 122 may include system operating softwarefor the video recorder device 102. For example, the system memory region122 may include an operating system, a video codec application, a userinterface application, any other instructions executable by the logic110 to perform the functions of the video recorder device 102, or anycombination thereof. In a particular illustrative embodiment, the systemmemory region 122 may be accessible to the service provider 104 toprovide updates to the system operating software. In this embodiment,the system memory region 122 may not be accessible to users of the videorecorder device 102. In an illustrative embodiment, an amount of memoryallocated to the system memory region 122 may be a preset value or maybe controlled by the service provider 104.

In a particular embodiment, the video receiver 112 may be adapted toaccess the memory device 120 to store received video data. In aparticular embodiment, the video receiver 112 may have access to aprotected memory region 124 of the memory device 120. The video receiver112 may store the received video data in the protected memory region124. The protected memory region 124 may be copy restricted, i.e., thevideo recorder device 102 may be adapted to prevent users from copyingvideo data stored in the protected memory region 124. In an illustrativeembodiment, an amount of memory allocated to the protected memory region124 may be a preset value and may not be adjustable by the user. Inanother illustrative embodiment, the amount of memory allocated to theprotected memory region 124 may be adjustable by the user. In anotherembodiment, the amount of memory allocated to the protected memoryregion 124 may be adjustable by the user within a predefined range.

In a particular embodiment, the memory device 120 may also include oneor more unprotected memory regions, such as a first unprotected memoryregion 126 and a second unprotected memory region 128. The one or moreunprotected memory regions 126, 128 may be accessible to the user viaone or more user device interlaces 114. The user may read data from orwrite data to the unprotected memory regions. In a particularembodiment, user access to the unprotected memory regions 126, 128 maybe controlled by a memory management policy 138. In an illustrativeembodiment, the number of unprotected memory regions and an amount ofmemory allocated to each unprotected memory region 126, 128 may beadjustable by the user.

In a particular embodiment, the video recorder device 102 may alsoinclude configuration records 130. The configuration records 130 mayinclude a partition record 134 and the memory management policy 138. Thepartition record 134 may specify the memory regions 122, 124, 126, 128of the memory device 120. For example, the partition record 134 maydefine specific sectors or regions of the memory device 120 that areassociated with particular memory regions. In a particular illustrativeembodiment, the memory regions 122, 124, 126, 128 may be logicalpartitions of the memory device 120. In a particular embodiment, thepartition record 134 may be modifiable based on user input. For example,the number of unprotected memory regions, an amount of memory allocatedto one or more of the memory regions, or any combination thereof may bemodified based on user input.

In a particular embodiment, the video recorder device 102 may include amemory controller 118. The memory controller 118 may control access tothe memory device 120. The memory controller 118 may include a partitioncontrol module 132 and a memory management module 136. In a particularembodiment, the partition control module 132 may maintain the partitionrecord 134. The partition control module 132 may modify the partitionrecord 134 based on user input. For example, the partition controlmodule 132 may modify the partition record 134 to adjust an amount ofmemory allocated to at least one of the protected memory region 124, thefirst unprotected memory region 126, the second unprotected memoryregion 128, or another memory region of the memory device 120. Thepartition control module 132 may also modify the partition record 134 tocreate or delete an unprotected memory region.

In a particular embodiment, the memory management module 136 maymaintain and implement the memory management policy 138. The memorymanagement policy 138 may specify access to particular regions of thememory device 120 and retention policies for particular regions of thememory device 120. The memory management policy 138 may be modifiablebased on user input. For example, a user may modify the memorymanagement policy 138 via a user interface to allow or restrict accessto particular regions of the memory device 120, to establish retentionpolicies for data in particular regions of the memory device 120, toestablish any other memory management policy, or any combinationthereof. The memory management module 136 may implement the memorymanagement policy 138 to restrict access to regions of the memory device120, to implement a retention policy regarding data stored in aparticular region of the memory device 120, to store particular types ofdata within specific regions of the memory device 120, to store datareceived from particular user device interfaces 114 in a specificregions of the memory device 120, or any combination thereof.

In a particular embodiment, the user device interface(s) 114 may includeone or more interfaces that allow user device(s) 140 to communicate withthe video recorder device 102. For example, the user device interface(s)114 may include a wireless network interface, a universal serial bus(USB) interface, a memory card reader, a local area network interface,such as an Ethernet port, a 1394 port, a serial port, a parallel port,any other user device interface, or any combination thereof. In aparticular embodiment, the user device interface(s) 114 may communicatedata between the user device 140 and at least one of the unprotectedmemory regions 126, 128. In a particular illustrative embodiment, thememory management policy 138 may specify which unprotected memory region126, 128 each of the user device interface(s) 114 may write to and readfrom. For example, the memory management policy 138 may specify thatdata received at a USB interface of the user device interface(s) 114 isto be stored at the first unprotected memory region 126.

In a particular embodiment, the memory management policy 138 may specifyparticular regions of the memory device 120 in which to store data basedon a file type of the data. For example, the memory management policy138 may specify that audio data, such as a Moving Picture Expert GroupAudio Layer-3 (mp3) file, is to be stored in the first unprotectedmemory region 126. In another example, the memory management policy 138may specify that images, photographs or graphics file types, such asGraphic Interchange Format (gif) files, are to be stored in the secondunprotected memory region 128.

In a particular embodiment, the video recorder device 102 may include auser interface module 116. The user interface module 116 may generate auser interface 142 at the display device 108. In an illustrativeembodiment, the user interface 142 may include video data received fromthe service provider 104, data received via the user device interfaces114, user interface control screens provided by the video recorderdevice 102, or any combination thereof. In a particular embodiment, theuser interface 142 may include user input elements that allow the userto access data stored at the memory device 120, or to modify theconfiguration records 130. For example, the user interface 142 mayinclude user input elements which allow the user to modify the partitionrecord 134 to add, delete or modify a memory region of the memory device120. In another particular embodiment, the user interface 142 mayinclude user input elements which allow the user to modify the memorymanagement policy 138. The user may interact with the user interface 142for example, via a remote control device 144.

FIG. 2 is flow chart of a first particular embodiment of a method ofstoring user data, generally designated 200. The method 200 includes, at206, receiving video data 202 via a video distribution network 204. Themethod 200 also includes, at 208, storing the video data 202 at aprotected memory region 210 of a memory device 212. In a particularembodiment, the memory device 212 may be adapted to prevent user copyingof data stored in the protected memory region 210.

The method 200 may also include, at 220, receiving user data 214. Forexample, the user data 214 may be received from a user device 216 via auser device interface 218. The user device interlace 218 may include,for example, a wireless network interface, a universal serial bus (USB)interface, a memory card reader, a local area network interface, such asan Ethernet port, a 1394 port, a serial port, a parallel port, any otheruser device interface, or any combination thereof.

The method 200 may also include, at 222, selecting one or more of theunprotected memory region(s) 224 in which to store the user data 214.For example, the one or more unprotected memory region(s) 224 may beselected based on a data type 226 of the user data 214. In anotherparticular illustrative embodiment, the one or more unprotected memoryregion(s) 224 may be selected based on the user device interface 218 viawhich the user data 214 is received. In a particular embodiment, themethod 200 may also include, at 228, storing the user data 214 at theselected unprotected memory region(s) 224.

In a particular embodiment, the method 200 may also include adjusting anamount of memory that is allocated to one or more of the protectedmemory region 210 or unprotected memory region(s) 224. For example, theuser data 214 may be too large to store in a first unprotected memoryregion. In this example, the user may reallocate memory from anothermemory region to the first unprotected memory region to increase theamount of memory available at the first unprotected memory regions.

FIG. 3 is flow diagram of a second particular embodiment of a method ofstoring user data, generally designated 300. The method 300 includes, at302, managing allocation of memory at a memory device 304. Managingallocation of memory 302 may include, at 308, receiving user input via afirst graphical user interface (GUI) 310. For example, the user inputmay include input to specify an additional unprotected memory region,input to modify memory allocated to one or more particular memoryregions, input to rename a memory region, input to delete a memoryregion (e.g., to remove a logical partition), or any combinationthereof. Managing allocation of the memory 302 may also include, at 312,modifying a memory allocation record 314. The memory allocation record314 may specify a plurality of memory regions of the memory device 304.For example, the memory allocation record 314 may include a partitionrecord which associates particular physical portions of the memorydevice 304 with logical memory partitions.

The method 300 also includes managing retention of user data, at 306. Ina particular embodiment, managing retention user data 306 may include,at 316, receiving user input via a second graphical user interface (GUI)318. Managing retention of user data 306 may also include, at 320,modifying memory management policies 322 based on the user input. In aparticular illustrative embodiment, each unprotected memory region of amemory device 304 may be associated with a memory management policy. Forexample, a first unprotected memory region 324 may be associated with afirst memory management policy 328, and a second unprotected memoryregion 326 may be associated with a second memory management policy 330,In a particular embodiment, the memory management policies 322 mayspecify user data to be stored in each unprotected memory region 324,326. For example, the first memory management policy 324 may specifyrules for storing user data 332 in the first unprotected memory region324. The memory management policies 322 may specify the rules forstoring the user data based on a file type of the user data, a userdevice interface from which the user data is received, any othercharacteristic of the user data or unprotected memory region, or anycombination thereof.

In a particular embodiment, the memory management policies 322 may alsospecify retention policies for user data 332, 334. For example, thememory management policies 322 may include retention policies associatedwith particular memory regions. A retention policy may specify when userdata may be overwritten, when user data may be deleted, when the usershould be provided with a warning regarding available capacity of aparticular memory region, or any combination thereof.

In a particular embodiment, managing retention of the user data 306 mayinclude, at 340, monitoring status information associated with thememory device 304 or the user data 332, 334. Monitoring statusinformation 340 may include monitoring time 342, monitoring particularthreshold levels 344, monitoring other information associated with thememory device, user data or retention policy, or any combinationthereof. In a particular embodiment, managing retention of user data 306may also include, at 336, notifying the user of status information. Inan illustrative embodiment, the retention policy may include a warningthreshold indicating that the user should be notified if the thresholdis exceeded. For example, the warning threshold may indicate that theuser should be notified if the capacity of the first unprotected memoryregion 324 reaches 90% (or any other user configurable threshold).

In a particular embodiment, monitoring retention of user data 306 mayalso include, at 338, deleting user data in accordance with themanagement policies 322. For example, the management policies 322 mayinclude a time limit associated with one or more of the unprotectedmemory regions 324, 326. The time limit may indicate that user datastored in the one or more unprotected memory regions 324, 326 may bedeleted after a specified period of time has elapsed. To illustrate, thefirst management policy 328 may include a time limit of 90 days forstorage of data at the first unprotected memory region 324. Thus, 90days after a user data file is stored at the first unprotected memoryregion 324, the user data file may be marked for deletion automaticallybased on the first management policy 328.

FIG. 4 is a diagram of a first particular embodiment of a user interfacefor storing user data, generally designated 400. The user interface 400includes information regarding a plurality of exemplary memory regionsidentified as video partition 402, security partition 404, musicpartition 406 and miscellaneous partition 408. The user interface 400also includes summary information regarding the memory device, such astotal memory 410 and available memory 412. The total memory 410 mayindicate the total physical memory of the memory device. The availablememory 412 may indicate the sum of unused or available memory in eachmemory region.

The user interface 400 may provide summary information regarding eachmemory region. For example, regarding the video partition 402, the userinterface 400 includes a text display 426 indicating that 200 gigabytesof memory from the memory device have been allocated to the videopartition 402. The text summary 426 also indicates that 150 gigabytes ofthe memory allocated to the video partition 402 have been used. Thesummary data regarding the video partition 402 also includes a graphicaldisplay 414 summarizing the disposition of memory within the videopartition 402. For example, the graphical display may include a bardiagram including a used region 416 indicating the portion of the videopartition 402 that is not available presently to store data, and anavailable region 418 indicating the portion of the video partition 402that is available to store data.

The user interface 400 may also include controls to modify allocation ofmemory in the memory device. For example, the user interface 400 mayinclude a graphical indicator 420 of an option to reduce an amount ofmemory allocated to the associated memory region. The user interface 400may also include a graphical indicator 422 of an option to increasememory allocated to the associated memory region. The user interface 400may also include a graphical indicator 424 of an option to modifyinformation associated with the particular memory region. For example,selecting the “manage” graphical indicator 424 may cause a userinterface such as the user interface 500 described with reference toFIG. 5 to be displayed. The user interface 400 may also include agraphical indicator 428 of an option to specify an additional memoryregion. Selecting the “add a partition” graphic indicator 428 may causea user interface such as the user interface 600 discussed with referenceto FIG. 6 to be displayed.

FIG. 5 is a diagram of a second particular embodiment of a userinterface for storing user data, generally designated 500. The userinterface 500 may include controls that allow a user to a modifyconfiguration record associated with a particular memory region. Asdepicted in FIG. 5, the user interface 500 is associated with the musicpartition 406 as depicted in FIG. 4. The user interface 500 may includesummary information regarding the particular memory region 502. Forexample, the user interface 500 may include an indication of a totalamount of memory allocated to the memory region. The user interface 500may also indicate how much of the allocated memory is used and how muchof the allocated memory that is unused or available for use.

In a particular embodiment, the user interface 500 may include agraphical indicator 504 of an option to rename the memory region. Afterselecting the “rename” graphical indicator 504, the user may be providedwith the opportunity to change a name associated with the memory region.In a particular embodiment, the user interface 500 may also include agraphical indicator 506 of an option to delete the memory region. In anillustrative embodiment, deleting the memory region includes deleting ormodifying a partition record that specifies the memory region. In aparticular illustrative embodiment, when a memory region is deleted, thememory associated with that memory region may be reallocated to adefault memory region. For example, the miscellaneous memory region 408depicted in FIG. 4 may be the default memory region. To illustrate,selection of the “delete” graphical indicator 506 associated with themusic partition may cause the 50 gigabytes of memory associated with themusic partition to be reallocated to the miscellaneous partition.

In a particular embodiment, the user interface 500 may also include agraphical indicator 508 of an option to modify a retention policyassociated with the memory region. For example, selecting the “retentionpolicy” graphical indicator 508 associated with the music partition maycause the user interface 700 depicted in FIG. 7 to be displayed. Theuser interface 500 may also include information about the retentionpolicy 516. The information about the retention policy 516 may include,for example, an overwrite policy 510, a delete policy 512, and a warningpolicy 514, which are discussed in more detail with reference to FIG. 7.

In a particular embodiment, the user interface 500 may include agraphical indicator 518 of an option to modify the memory managementpolicy associated with the memory region. For example, selecting the“memory management policy” graphical indicator 518 associated with themusic partition may allow the user to modify the memory managementpolicy associated with the music partition memory region via a userinterface such as the user interface 800 depicted in FIG. 8. The userinterface 500 may also include information about the memory managementpolicy. The information about the memory management policy may includefor example, a storage policy 520. The storage 520 may indicate datatypes or user interfaces associated with the particular memory region.

FIG. 6 depicts a diagram of a third particular embodiment of a userinterface of a system for storing user data, generally designated 600.The user interface 600 includes a graphical indicator 602 of an optionto name a new memory region created in response to user input. The userinterface 600 also includes a graphical indicator 604 specifying a sizeof the new memory region. The user interface 600 also includes graphicalindicators 606 of an option to increase or decrease the amount of memoryallocated for the new memory partition. The user interface 600 may alsoinclude summary information regarding the new memory region or thememory device. For example, the summary information 608 providesinformation regarding total available memory of the memory device and anamount of memory available in a default memory region. Memory allocatedto the new memory region will be from the default memory region unlessotherwise specified by the user. For example, the “Take Memory From”area 610 includes a graphical indicator 612 of an option to designate anexisting memory region from which memory should be taken. Themiscellaneous partition is indicated to be the default memory region at614. Thus, for example, the user may select a graphical indicatorassociated with one or more existing memory regions to indicate thatmemory allocated to the new memory region should be taken from theselected memory regions.

FIG. 7 is a diagram of a fourth particular embodiment of a userinterface of a system for storing user data, generally designated 700.The user interface 700 includes a plurality of controls to modify orestablish a retention policy associated with a particular memory region,such as the music partition. The user interface 700 includes anoverwrite policy area 702, a delete policy area 704, and a warningpolicy area 706. The overwrite policy area 702 includes controlsallowing the user to specify an overwrite policy associated with aparticular memory region. In an illustrative embodiment, the overwritepolicy specify that data stored in the memory region should be markedfor overwriting after a specific time period has elapsed. For example,after selecting overwrite after graphical indicator 702 a user mayspecify a particular number of days after which data stored in thememory region may be overwritten at graphical indicator 714. Theoverwrite policy area 702 may also include a graphical indicator 710 ofan option to indicate that data stored within the memory region may beoverwritten when capacity of the memory region is reached. The overwritepolicy area 702 may also include a graphical indicator 712 of an optionto indicate that the data stored in the particular memory should neverbe automatically overwritten.

The delete policy area 704 may include a graphical indicator 716 of anoption to indicate that data stored in the particular memory region maybe automatically deleted after a specified time period 720. The deletepolicy region 704 may also include a graphical indicator 718 of anoption to indicate that data stored in the particular memory regionshould never be automatically deleted.

The warning policy area 706 may include a graphical indicator 722 of anoption to indicate that the user should be provided a warning when aspecified capacity threshold limit 726 is reached. The warning policyarea 706 may also include a graphical indicator 724 of an option toindicate that warnings should not be provided to the user based oncapacity available at the memory region.

FIG. 8 is a diagram of a fifth particular embodiment of a user interfaceof a system for storing user data, generally designated 800. The userinterface 800 provides controls for configuring a memory managementpolicy. For example, the user interface 800 may include a file type area802. The file type area 802 may include a plurality of graphicalindicators 804, 808 of options to associate particular types of fileswith the memory region. For example, by selecting music files graphicalindicator 804 recognized music file types may be associated with themusic partition. In a particular embodiment, the types of filesavailable for selection in the file type area 802 may be input by theuser. In another particular embodiment, the types of files available forselection in the file type area 802 may be provided by a serviceprovider. For example, by selecting graphical indicator 808, the typesof files available to be associated with the memory region may beupdated by a server at the service provider.

The user interface 800 may also include an input area 810. The inputarea 810 may allow the memory region to be associated with one or moreuser device interfaces. For example, by selecting one or more of thegraphical indicators 812, the user may associate the music partitionwith a USB port 1, a USB port 2, a 1394 port, a Ethernet port or a cardreader port.

In conjunction with the configuration of structure described herein, thesystems and methods disclosed may store user data. In a particularembodiment, video data may be received at a video recorder device via avideo distribution network. The video recorder device may store thevideo data at a protected memory region of a memory device. The memorydevice may be adapted to prevent user copying of data stored in theprotected memory region. The video recorder device may also receive userdata via a user device interface. The video recorder device may storethe user data at an unprotected memory region of the memory device. Thememory device may be adapted to allow user copying of data stored in theunprotected memory region.

Referring to FIG. 9, an illustrative embodiment of a general computersystem is shown and is designated 900. The computer system 900 caninclude a set of instructions that can be executed to cause the computersystem 900 to perform any one or more of the methods or computer basedfunctions disclosed herein. The computer system 900 may operate as astandalone device or may be connected, e.g., using a network, to othercomputer systems or peripheral devices. For example, the computer systemmay include any one or more of the user devices, video recorder devices,memory devices or other devices depicted in FIG. 1, 2 or 3.

In a networked deployment, the computer system may operate in thecapacity of a server or as a client user computer in a server-clientuser network environment, or as a peer computer system in a peer-to-peer(or distributed) network environment. The computer system 900 can alsobe implemented as or incorporated into various devices, such as apersonal computer (PC), a tablet PC, a set-top box (STB), a personaldigital assistant (PDA), a mobile device, a palmtop computer, a laptopcomputer, a desktop computer, a communications device, a wirelesstelephone, a land-line telephone, a control system, a camera, a scanner,a facsimile machine, a printer, a pager, a personal trusted device, aweb appliance, a network router, switch or bridge, or any other machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. In a particularembodiment, the computer system 900 can be implemented using electronicdevices that provide voice, video or data communication. Further, whilea single computer system 900 is illustrated, the term “system” shallalso be taken to include any collection of systems or sub-systems thatindividually or jointly execute a set, or multiple sets, of instructionsto perform one or more computer functions.

As illustrated in FIG. 9, the computer system 900 may include aprocessor 902, e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), or both. Moreover, the computer system 900 caninclude a main memory 904 and a static memory 906, that can communicatewith each other via a bus 908. As shown, the computer system 900 mayfurther include a video display unit 910, such as a liquid crystaldisplay (LCD), an organic light emitting diode (OLED), a flat paneldisplay, a solid state display, or a cathode ray tube (CRT).Additionally, the computer system 900 may include an input device 912,such as a keyboard, and a cursor control device 914, such as a mouse.The computer system 900 can also include a disk drive unit 916, a signalgeneration device 918, such as a speaker or remote control, and anetwork interface device 920.

In a particular embodiment, as depicted in FIG. 9, the disk drive unit916 may include a computer-readable medium 922 in which one or more setsof instructions 924, e.g. software, can be embedded. Further, theinstructions 924 may embody one or more of the methods or logic asdescribed herein. In a particular embodiment, the instructions 924 mayreside completely, or at least partially, within the main memory 904,the static memory 906, and/or within the processor 902 during executionby the computer system 900. The main memory 904 and the processor 902also may include computer-readable media.

In an alternative embodiment, dedicated hardware implementations, suchas application specific integrated circuits, programmable logic arraysand other hardware devices, can be constructed to implement one or moreof the methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations.

In accordance with various embodiments of the present disclosure, themethods described herein may be implemented by software programsexecutable by a computer system. Further, in an exemplary, non-limitedembodiment, implementations can include distributed processing,component/object distributed processing, and parallel processing.Alternatively, virtual computer system processing can be constructed toimplement one or more of the methods or functionality as describedherein.

The present disclosure contemplates a computer-readable medium thatincludes instructions 924 or receives and executes instructions 924responsive to a propagated signal, so that a device connected to anetwork 926 can communicate voice, video or data over the network 926.Further, the instructions 924 may be transmitted or received over thenetwork 926 via the network interface device 920.

While the computer-readable medium is shown to be a single medium, theterm “computer-readable medium” includes a single medium or multiplemedia, such as a centralized or distributed database, and/or associatedcaches and servers that store one or more sets of instructions. The term“computer-readable medium” shall also include any medium that is capableof storing, encoding or carrying a set of instructions for execution bya processor or that cause a computer system to perform any one or moreof the methods or operations disclosed herein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to capturecarrier wave signals such as a signal communicated over a transmissionmedium. A digital file attachment to an e-mail or other self-containedinformation archive or set of archives may be considered a distributionmedium that is equivalent to a tangible storage medium. Accordingly, thedisclosure is considered to include any one or more of acomputer-readable medium or a distribution medium and other equivalentsand successor media, in which data or instructions may be stored.

Although the present specification describes components and functionsthat may be implemented in particular embodiments with reference toparticular standards and protocols, the disclosed embodiments are notlimited to such standards and protocols. For example, standards forInternet and other packet switched network transmission (e.g., TCP/IP,UDP/IP, HTML, HTTP) represent examples of the state of the art. Suchstandards are periodically superseded by faster or more efficientequivalents having essentially the same functions. Accordingly,replacement standards and protocols having the same or similar functionsas those disclosed herein are considered equivalents thereof.

The illustrations of the embodiments described herein are intended toprovide a general understanding of the structure of the variousembodiments. The illustrations are not intended to serve as a completedescription of all of the elements and features of apparatus and systemsthat utilize the structures or methods described herein. Many otherembodiments may be apparent to those of skill in the art upon reviewingthe disclosure. Other embodiments may be utilized and derived from thedisclosure, such that structural and logical substitutions and changesmay be made without departing from the scope of the disclosure.Additionally, the illustrations are merely representational and may notbe drawn to scale. Certain proportions within the illustrations may beexaggerated, while other proportions may be reduced. Accordingly, thedisclosure and the figures are to be regarded as illustrative ratherthan restrictive.

One or more embodiments of the disclosure may be referred to herein,individually and/or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any particular invention or inventive concept. Moreover,although specific embodiments have been illustrated and describedherein, it should be appreciated that any subsequent arrangementdesigned to achieve the same or similar purpose may be substituted forthe specific embodiments shown. This disclosure is intended to cover anyand all subsequent adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b) and is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, various features may begrouped together or described in a single embodiment for the purpose ofstreamlining the disclosure. This disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may be directed toless than all of the features of any of the disclosed embodiments. Thus,the following claims are incorporated into the Detailed Description,with each claim standing on its own as defining separately claimedsubject matter.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present invention. Thus, to the maximumextent allowed by law, the scope of the present invention is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A video recorder device, comprising: a videoreceiver to receive video data; and a memory device including: at leastone protected memory region to store video data received via the videoreceiver, wherein the video recorder device is adapted to prevent usercopying of video data stored at the protected memory region video datastored at the at least one protected memory region is copy restrictedand is accessible for display at a display device; and at least oneunprotected memory region, wherein the video recorder device is adaptedto allow user copying of data stored at the unprotected memory region isuser modifiable.
 2. The video recorder device of claim 1, furthercomprising a partition control module to maintain a partition record,wherein the partition record relates the at least one protected memoryregion and the at least one unprotected memory region to a memory mediumof the memory device.
 3. The video recorder device of claim 2, whereinthe partition control module is operable to modify the partition recordbased on user input to adjust an amount of memory allocated to the atleast one protected memory region.
 4. The video recorder device of claim2, wherein the partition control module is operable to modify thepartition record based on user input to adjust an amount of memoryallocated to the at least one unprotected memory region.
 5. The videorecorder device of claim 1, further comprising a memory managementmodule to implement a user configurable memory management policyassociated with the at least one unprotected memory region.
 6. The videorecorder device of claim 1, further comprising at least one user deviceinterface to communicate data between a user device and the at least oneunprotected memory region.
 7. The video recorder device of claim 1,wherein the at least one user device interface comprises a wirelessnetwork interface.
 8. The video recorder device of claim 1, wherein theat least one user device interface comprises a universal serial bus(USB) interface.
 9. The video recorder device of claim 1, wherein the atleast one user device interface comprises a local area networkinterface.
 10. The video recorder device of claim 1, further comprisinga plurality of user device interfaces and a plurality of unprotectedmemory regions, wherein each of the user device interfaces is associatedwith at least one of the unprotected memory regions.
 11. The videorecorder device of claim 1, further comprising a user interface moduleto display a user interface at a display device and to receive userconfiguration input to modify a configuration record associated with thememory device.
 12. The video recorder device of claim 1, the userinterface includes a representation of an amount of memory availablewithin the at least one protected memory region and within the at leastone unprotected memory region.
 13. The video recorder device of claim 1,the user interface includes at least one user selectable element toassociate the at least one unprotected memory region with at least onefile type.
 14. The video recorder device of claim 1, further comprisinga system memory region, wherein the system memory region is accessibleto a service provider via the video receiver.
 15. The video recorderdevice of claim 1, further comprising a memory controller and aplurality of unprotected memory regions, wherein the memory controlleris operable to select a region from among the plurality of unprotectedmemory regions in which to store particular data based on a type of thedata.
 16. A method comprising: receiving video data via a videodistribution network; storing the video data at a protected memoryregion of a memory device, wherein the memory device is adapted toprevent user copying of video data stored in at the protected memoryregion is copy restricted and is accessible for display at a displaydevice; receiving user data via a user device interface; and storing theuser data at an unprotected memory region of the memory device, whereinthe memory device is adapted to allow user copying of user data storedin the unprotected memory region is user modifiable.
 17. The method ofclaim 16, wherein the memory device includes a plurality of unprotectedmemory regions, and wherein the method further comprises storing theuser data at two or more of the plurality of unprotected memory regions.18. The method of claim 17, further comprising selecting one of theplurality of unprotected memory regions in which to store particularuser data based on a type of the particular user data.
 19. The method ofclaim 16, wherein a user configurable memory management policy isassociated with the unprotected memory region.
 20. The method of claim19, further comprising deleting the user data stored at the unprotectedmemory region based on the user configurable memory management policy.21. The method of claim 19, further comprising receiving userconfiguration input via a graphical user interface, and modifying theuser configurable memory management policy based on the userconfiguration input.
 22. The method of claim 16, further comprisingreceiving user configuration input via a graphical user interface, andmodifying an amount of memory allocated to the unprotected memory regionbased on the user configuration input.
 23. A processor readable mediummemory device comprising processor readable instructions, wherein theprocessor readable instructions are executable by a processor to:receive video data via a video distribution network; store the videodata at a protected memory region of a memory device, wherein the memorydevice is adapted to prevent user copying of video data stored in theprotected memory region is copy restricted and is accessible for displayat a display device; receive user data via at least one user deviceinterface; and store the user data at one or more unprotected memoryregions of the memory device, wherein the memory device is adapted toallow user copying of user data stored in the one or more unprotectedmemory regions is user modifiable.
 24. The processor readable mediummemory device of claim 23, further comprising processor readableinstructions executable to manage allocation of memory among theprotected memory region and the one or more unprotected memory regions.25. The processor readable medium memory device of claim 23, furthercomprising processor readable instructions executable to select one ofthe one or more unprotected memory regions at which to store particularuser data.
 26. The processor readable medium memory device of claim 23,further comprising processor readable instructions executable to selectone of the one or more unprotected memory regions at which to storeparticular user data based on the at least one user device interface viawhich the particular user data was received.
 27. The processor readablemedium memory device of claim 23, further comprising processor readableinstructions executable to manage retention of the user data based onone or more memory management policies.
 28. The processor readablemedium memory device of claim 27, further comprising processor readableinstructions executable to receive user input to modify the one or morememory management policies.
 29. A method comprising: receiving firstdata at a video playback device, the first data received by the videoplayback device via a distribution network; storing the first data at afirst memory region of a memory device accessible to the video playbackdevice, wherein the first data stored at the first memory region is copyrestricted and is accessible for display at a display device; receivingsecond data via a graphical user interface (GUI) of the video playbackdevice; and storing the second data at a second memory region of thememory device, wherein the second data stored at the second memoryregion is user modifiable.
 30. The method of claim 29, furthercomprising, in response to a user request, displaying video content thatcorresponds to the first data.
 31. The method of claim 30, wherein thevideo content comprises television programming.
 32. The method of claim29, wherein the first data includes video data, and wherein the seconddata includes user data.
 33. The method of claim 29, wherein the videoplayback device includes the memory device and further includes aprocessor coupled to the memory device.
 34. The method of claim 29,wherein the distribution network is a video distribution network. 35.The method of claim 29, wherein the video playback device includes adisplay, and wherein the GUI is provided at the display.
 36. The methodof claim 29, wherein the video playback device includes a video recorderdevice.
 37. The method of claim 29, wherein the video playback deviceincludes a gaming system.
 38. The method of claim 29, wherein the videoplayback device includes a mobile device.
 39. The method of claim 29,wherein the video playback device includes a computer.
 40. The method ofclaim 29, wherein the video playback device includes a portablecomputer.
 41. A method comprising: storing first data at a first memoryportion of a memory system, wherein the first data stored at the firstmemory portion is copy restricted and is accessible for display at adisplay device; receiving second data at a video playback device; andstoring the second data at a second memory portion of the memory system,wherein the second data stored at the second memory portion ismodifiable by a user of the video playback device.
 42. The method ofclaim 41, further comprising, in response to a user request, sending thefirst data via a distribution network to the video playback device toenable the video playback device to display video content correspondingto the first data.
 43. The method of claim 42, wherein sending the firstdata to the video playback device includes streaming the video contentto the video playback device.
 44. The method of claim 43, wherein thevideo content is streamed to the video playback device in accordancewith a protocol comprising an internet protocol, a transmission controlprotocol, a user datagram protocol, a hypertext transfer protocol, or acombination thereof.
 45. The method of claim 41, wherein the user of thevideo playback device is permitted to read from the first data stored atthe first memory portion, and wherein the user is not permitted to writeto the first data stored at the first memory portion.
 46. The method ofclaim 41, further comprising: receiving updated second data from thevideo playback device; and modifying the second data stored at thesecond memory portion of the memory system based on the updated seconddata.
 47. A computer-readable storage device comprising instructionsthat are executable by a processor of a video playback device to performoperations comprising: receiving first data at the video playbackdevice, the first data received by the video playback device via adistribution network, wherein the first data corresponds to televisionprogramming; storing the first data at a first memory region of a memorydevice within the video playback device, wherein the first data storedat the first memory region is copy restricted and is accessible fordisplay at a display device; receiving second data via a graphical userinterface (GUI) of the video playback device; and storing the seconddata at a second memory region of the memory device, wherein the seconddata stored at the second memory region of the memory device ismodifiable by a user of the video playback device.
 48. Thecomputer-readable storage device of claim 47, further comprising, inresponse to a user request, displaying video content corresponding tothe first data.
 49. The computer-readable storage device of claim 47,wherein the first data is received at the video playback device inaccordance with a protocol comprising an internet protocol, atransmission control protocol, a user datagram protocol, a hypertexttransfer protocol, or a combination thereof.
 50. The computer-readablestorage device of claim 47, wherein the video playback device includes agaming system, a mobile device, a computer, or a portable computer. 51.The computer-readable storage device of claim 47, wherein the videoplayback device includes a serial bus interface and a network interface.52. A video recorder device, comprising: a video receiver to receivedata; and a memory device including: at least one protected memoryregion to store first data received via the video receiver, wherein thefirst data stored at the at least one protected memory region is copyrestricted and is accessible for display at a display device; and atleast one unprotected memory region, wherein second data stored at theat least one unprotected memory region is user modifiable.
 53. The videorecorder device of claim 52, further comprising a partition controlmodule to maintain a partition record, wherein the partition recordrelates the at least one protected memory region and the at least oneunprotected memory region to a memory medium of the memory device. 54.The video recorder device of claim 53, wherein the partition controlmodule is operable to modify the partition record based on user input toadjust an amount of memory allocated to the at least one protectedmemory region.
 55. The video recorder device of claim 53, wherein thepartition control module is operable to modify the partition recordbased on user input to adjust an amount of memory allocated to the atleast one unprotected memory region.
 56. The video recorder device ofclaim 52, further comprising a memory management module to implement auser configurable memory management policy associated with the at leastone unprotected memory region.
 57. The video recorder device of claim52, further comprising at least one user device interface to communicatedata between a user device and the at least one unprotected memoryregion.
 58. The video recorder device of claim 57, wherein the at leastone user device interface comprises a wireless network interface. 59.The video recorder device of claim 57, wherein the at least one userdevice interface comprises a universal serial bus (USB) interface. 60.The video recorder device of claim 57, wherein the at least one userdevice interface comprises a local area network interface.
 61. The videorecorder device of claim 52, further comprising a plurality of userdevice interfaces and a plurality of unprotected memory regions, whereineach of the user device interfaces is associated with at least one ofthe unprotected memory regions.
 62. The video recorder device of claim52, further comprising a user interface module to display a graphicaluser interface (GUI) at a display device and to receive userconfiguration input to modify a configuration record associated with thememory device.
 63. The video recorder device of claim 62, wherein theuser interface includes a presentation of a first amount of memoryavailable within the at least one protected memory region and a secondamount of memory available within the at least one unprotected memoryregion.
 64. The video recorder device of claim 63, wherein the userinterface includes at least one user selectable element to associate theat least one unprotected memory region with at least one file type. 65.The video recorder device of claim 52, further comprising a systemmemory region, wherein the system memory region is accessible to aservice provider via the video receiver.
 66. The video recorder deviceof claim 52, further comprising a memory controller and a plurality ofunprotected memory regions, wherein the memory controller is operable toselect a region from among the plurality of unprotected memory regionsin which to store particular data based on a type of the particulardata.
 67. A method comprising: receiving first data via a distributionnetwork; storing the first data at a protected memory region of a memorydevice, wherein the first data stored at the protected memory region iscopy restricted and is accessible for display at a display device;receiving second data via a user device interface; and storing thesecond data at an unprotected memory region of the memory device,wherein the second data stored at the unprotected memory region is usermodifiable.
 68. The method of claim 67, wherein the memory deviceincludes a plurality of unprotected memory regions, and wherein themethod further comprises storing the second data at two or more of theplurality of unprotected memory regions.
 69. The method of claim 68,further comprising selecting one of the plurality of unprotected memoryregions in which to store particular user data based on a type of theparticular user data.
 70. The method of claim 67, wherein a userconfigurable memory management policy is associated with the unprotectedmemory region.
 71. The method of claim 70, further comprising deletingthe second data stored at the unprotected memory region based on theuser configurable memory management policy.
 72. The method of claim 70,further comprising receiving user configuration input via a graphicaluser interface, and modifying the user configurable memory managementpolicy based on the user configuration input.
 73. The method of claim67, further comprising receiving user configuration input via agraphical user interface, and modifying an amount of memory allocated tothe unprotected memory region based on the user configuration input. 74.A processor readable device comprising processor readable instructions,wherein the processor readable instructions are executable by aprocessor to: receive first data via a distribution network; store thefirst data at a protected memory region of a memory device, wherein thefirst data stored at the protected memory region is copy restricted andaccessible for display at a display device; receive second data via atleast one user device interface; and store the second data at one ormore unprotected memory regions of the memory device, wherein the seconddata stored at the one or more unprotected memory regions is usermodifiable.
 75. The processor readable device of claim 74, furthercomprising processor readable instructions executable to manageallocation of memory among the protected memory region and the one ormore unprotected memory regions.
 76. The processor readable device ofclaim 74, further comprising processor readable instructions executableto select one of the one or more unprotected memory regions at which tostore particular user data.
 77. The processor readable device of claim74, further comprising processor readable instructions executable toselect one of the one or more unprotected memory regions at which tostore particular user data based on the at least one user deviceinterface via which the particular user data was received.
 78. Theprocessor readable device of claim 74, further comprising processorreadable instructions executable to manage retention of the second databased on one or more memory management policies.
 79. The processorreadable device of claim 78, further comprising processor readableinstructions executable to receive user input to modify the one or morememory management policies.